Resource-based boot sequence

ABSTRACT

A computer-implemented method, for booting a computer system, that provides a list with entries of startup processes. Each startup process defines a resource of the computer system. For each startup process a requirement is defined. The method further comprises fetching one of the entries of the list with entries of startup processes; determining whether the requirement is satisfied for the one of the entries of the list with entries of startup processes; fetching, in case the requirement is not fulfilled, a next one of the entries of the list with entries of startup processes; starting, in case the required resource is fulfilled, the startup process; and repeating the fetching a next one of the entries, the determining and the starting until all startup processes of the list of startup processes have been started.

BACKGROUND OF THE INVENTION

The invention relates generally to a computer-implemented method forbooting a computer system, and more specifically, to a resource-basedboot sequence. The invention relates further to a related boot modulefor booting a computer system, and a computer program product. Today'scomputing centers—in particular cloud computing centers and also hybridapproaches—rely heavily on virtual machines as a key delivery mechanismfor providing ad-hoc IT (information technology) resources for pilotprojects, testing purposes and also for production environments. In sucha context, it is paramount to set up virtual machines in virtually notime, i.e., the time required for booting the virtual machine becomes acritical parameter.

Today, upon a boot request for a virtual machine, the virtual machine isconstructed with all resources available, i.e., after all requestedvirtual CPUs, memory resources and devices are available for the newvirtual machine. This may cause some delays in booting the virtualmachine. Given the sheer size of today's systems—e.g., terabytes ofmemory, hundred or more CPUs, and so on—it becomes uneconomical tofirstly construct the container for the virtual machine with allresources before booting the system because it may imply clearing aterabyte of requested memory. On the other hand, booting a system ofvirtual machines before all resources are available may cause unexpectedfailures during the startup of services. A simple example may be anout-of-memory situation due to the fact that at a certain point in time,during the boot process, sufficient memory is not available.

SUMMARY

According to one aspect of the present invention, a computer-implementedmethod for booting a computer system may be provided. The method maycomprise providing a list comprising entries of startup processes. Eachstartup process may define a resource of the computer system. For eachstartup process a requirement may be defined. It may also be noted thatthe provided list may be named extended boot sequence table.

The method may further comprise fetching one of the entries of the listwith entries of startup processes, determining whether the requirementis satisfied for the one of the entries of the list with entries ofstartup processes, fetching, in case the requirement is not fulfilled, anext one of the entries of the list with entries of startup processes,starting, in case the required resource is fulfilled, the startupprocess, and repeating the fetching a next one of the entries, thedetermining and the starting until all startup processes of the list ofstartup processes have been started.

According to another aspect of the present invention, a boot module forbooting a computer system may be provided. The boot module may comprisean extended boot sequence table providing unit configured to provide alist with entries of startup processes. Each startup process may definea—required—resource of the computer system and for each startup processa requirement may be defined.

The boot module may additionally comprise a fetching unit configured tofetch one of the entries of the list with entries of startup processes,a determining unit configured to determine whether the requirement issatisfied for the one of the entries of the list with entries of startupprocesses. The fetching unit may also be configured to fetch, in casethe requirement is not fulfilled, a next one of the entries of the listwith entries of startup processes.

Furthermore, the boot module may comprise a start module configured tostart, in case the required resource is fulfilled, the startup process.The fetching unit, the determining unit and the start unit may, incombination, be configured to repeat the fetching a next one of theentries, the determining and the starting until all startup processes ofthe list of startup processes have been started.

Furthermore, embodiments may take the form of a related computer programproduct, accessible from a computer-usable or computer-readable mediumproviding program code for use, by or in connection with a computer orany instruction execution system. For the purpose of this description, acomputer-usable or computer-readable medium may be any apparatus thatmay contain means for storing, communicating, propagating ortransporting the program for use, by or in a connection with theinstruction execution system, apparatus, or device.

BRIEF DESCRIPTION OF THE DRAWINGS

It should be noted that embodiments of the invention are described withreference to different subject-matters. In particular, some embodimentsare described with reference to method type claims whereas otherembodiments have been described with reference to apparatus type claims.However, a person skilled in the art will gather from the above and thefollowing description that, unless otherwise notified, in addition toany combination of features belonging to one type of subject-matter,also any combination between features relating to differentsubject-matters, in particular, between features of the method typeclaims, and features of the apparatus type claims, is considered as tobe disclosed within this document.

The aspects defined above and further aspects of the present inventionare apparent from the examples of embodiments to be describedhereinafter and are explained with reference to the examples ofembodiments, but to which the invention is not limited.

Preferred embodiments of the invention will be described, by way ofexample only, and with reference to the following drawings:

FIG. 1 shows a block diagram of a computer-implemented method forbooting a computer system in accordance with at least one embodiment ofthe present invention;

FIG. 2 shows a block diagram of a known boot process;

FIG. 3 shows a block diagram of a boot process in accordance with atleast one embodiment of the present invention;

FIG. 4 shows a more comprehensive block diagram of method in accordancewith at least one embodiment of the present invention;

FIG. 5 shows the wait sub-process of FIG. 4, in accordance with at leastone embodiment of the present invention;

FIG. 6 shows a state diagram for a state engine corresponding to amethod, in accordance with at least one embodiment of the presentinvention;

FIG. 7 shows a boot module for booting a computer system in accordancewith at least one embodiment of the present invention;

FIG. 8 shows a cloud computing environment in accordance with at leastone embodiment of the present invention; and

FIG. 9 shows a computing system comprising a boot module in accordancewith at least one embodiment of the present invention.

DETAILED DESCRIPTION

In the context of this description, the following conventions, termsand/or expressions may be used:

The term ‘booting’ (or booting up) may denote an initialization of acomputerized system. The system may be a computer or a computerappliance (a read or a virtual system). The booting process may be“hard”, e.g., after electrical power to the CPU is switched from “off”to “on” (in order to diagnose particular hardware errors), or “soft”,when those power-on self-tests (POST) can be avoided. On some systems, asoft boot may optionally clear the memory to zero. Both, hard and softbooting may be initiated by hardware such as a button press, or by asoftware command. Booting may be complete when the normal, operative,runtime environment is attained. A boot-loader may be instrumental forbooting a system. Typically, a minimal set of resources may be requiredfor specific portions of the boot process. For example, a softwarecomponent as part of a boot process may not fit into the available mainmemory for execution. In such a case, the boot process cannot becontinued with this component until the resource may become available.However, it may be continued with other required components requiringless resources.

The term ‘startup processes’ or process may denote an instance of acomputer program—or a part thereof—that is being executed. It containsthe program code and its current activity. In this sense, a startupprocess is a process required for a startup or booting of a computer.Depending on the operating system (OS), a process may be made up ofmultiple threads of execution that execute instructions concurrently.

The term ‘resource’ may denote a hardware or a software componentrequired to perform a task, like executing program code of a process.Examples of resources are a CPU (central processing unit), memory in anyform (main memory, hard drive storage, cache memory, shared memory incase of multiprocessor systems), an input/output adapter, acommunication channel, a peripheral device, address space, a mathematiccoprocessor, a crypto-processor, a CPU core, and the like. The requiredresource may represent a “must-have” for a process in order to run theprocess.

The term ‘wait status’ may denote the opposite status to a “run status”or “execute status”. In the wait status a process may not proceed withits execution. The process may simply wait before a clearance is givento execute next program or process steps. Alternatively, the process maybe hibernated, interrupted or stopped with the option to continueexecution if the reason for the halt may be gone.

The term ‘virtual machine’ (VM) may denote an emulation of a computersystem. Virtual machines may be based on computer architectures and mayprovide functionality of a physical computer. Their implementations mayinvolve specialized hardware, software, or a combination. VMs mayprovide a substitute for a real machine. They provide functionalityneeded to execute entire operating systems. A hypervisor may use nativeexecution to share and manage hardware, allowing for multipleenvironments which are isolated from one another, yet exist on the samephysical machine. Modern hypervisors may use hardware-assistedvirtualization, virtualization-specific hardware, primarily from thehost CPUs.

The term ‘daemon’, may denote—in particular in multitasking computeroperating systems a computer program that may run as a backgroundprocess, rather than being under the direct control of an interactiveuser.

In this document, cloud computing services, cloud computing environmentsand virtual machines are mentioned several times. Such services maybelong to cloud computing in general, which may be a model for enablingconvenient, on-demand network access to a shared pool of configurablecomputing resources (e.g., networks, servers, storage, applications, andservices) that may be rapidly provisioned and released with minimalmanagement effort or service provider interaction. This cloud model maypromote availability and may be composed of five essentialcharacteristics, three service models and four deployment models.

Essential Characteristics of cloud computing comprise

(i) On-demand self-service: A consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with eachservice provider.

(ii) Broad network access: Capabilities are available over the networkand accessed through standard mechanisms that promote use byheterogeneous thin or thick client platforms (e.g., mobile phones,laptop computers, tablet computers, and PDAs).

(iii) Resource pooling: The provider's computing resources are pooled toserve multiple consumers using a multi-tenant model with differentphysical and virtual resources, dynamically assigned and reassignedaccording to consumer demand. There is a sense of location independencein that the customer generally has no control or knowledge over theexact location of the provided resources, but may be able to specifylocation at a higher level of abstraction (e.g., country, state, ordatacenter). Examples of resources include storage, processing, memory,network bandwidth and virtual machines.(iv) Rapid elasticity: Capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly release to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.(v) Measured Service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled and reported providing transparency for both, theprovider and consumer of the utilized service.

Service models for cloud computing used comprise:

(i) Cloud Software as a Service (SaaS): The capability provided to theconsumer is to use the provider's applications running on a cloudinfrastructure. The applications are accessible from various clientdevices through a thin client interface such as a Web browser (e.g.,Web-based e-mail). The consumer does not manage or control theunderlying cloud infrastructure including network, servers, operatingsystems, storage, or even individual application capabilities, with thepossible exception of limited user-specific application configurationsettings.(ii) Cloud Platform as a Service (PaaS): The capability provided to theconsumer is to deploy onto the cloud infrastructure consumer-created oracquired applications created using programming languages and toolssupported by the provider. The consumer does not manage or control theunderlying cloud infrastructure including network, servers, operatingsystems, or storage, but has control over the deployed applications andpossibly applications hosting environment configurations.(iii) Cloud Infrastructure as a Service (IaaS): The capability providedto the consumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure, but has control over operating systems, storage,deployed applications, and possibly limited control of selectednetworking components (e.g., host firewalls).

Deployment models for cloud computing comprise

(i) Private cloud. The cloud infrastructure is operated solely by anorganization. It may be managed by the organization or a third party andmay exist on premise or off premise.

(ii) Community cloud. The cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on premise or off premise.(iii) Public cloud. The cloud infrastructure is made available to thegeneral public or a large industry group and is owned by an organizationselling cloud services, e.g., a cloud service provider.(iv) Hybrid cloud. The cloud infrastructure is a composition of two ormore clouds (private, community, or public) that remain unique entitiesbut are bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

It may be noted that cloud software may take full advantage of the cloudparadigm by being service-oriented with a focus on statelessness, lowcoupling, modularity, and semantic interoperability.

The disclosed computer-implemented method for booting a computer systemmay offer multiple advantages and technical effects:

Waiting until all requested resources for a new virtual (or real)machine to be booted may be avoided. This may decrease the time requiredto boot a new virtual machine. By making startup processes depending onindividual requirements, i.e., required resources for this particularstartup process, not all prerequisites must be met before the completestartup procedure or boot sequence table may be executed. Hence,individual startup processes, which requirements or prerequisite(s) mayalready be met may, be started even before requirements for all startupprocesses may be fulfilled.

As a consequence, those startup processes of the extended boot sequencetable which requirements are fulfilled may be started immediately,whereas other startup processes which prerequisites are not fulfilledyet may be put in a wait status, i.e., delayed. At the time aprerequisite for another startup process may be fulfilled, the relatedwait status may be released and the additional startup process may beinitiated. At the same time, the other startup processes—whichrequirements have been fulfilled before—are already up and running.

That way, the startup processes are initiated and executed in a flexiblesequence the requirements are fulfilled and not in a static predefinedway. If a startup process may not be started due to a not fulfilledrequirement, other startup processes which requirements may already befulfilled may be started. The time for the startup processes may bedenoted as the waiting time for the startup process which requirementshave not been fulfilled at the start of an extended boot sequence table.Thus, the risk of a blocking of an extended boot sequence table may bereduced significantly because a startup process may be started as soonas the related requirement is fulfilled. The execution of the bootsequence table may not be delayed completely until all requirements forall startup processes may be fulfilled at one point in time. Hence, thestartup process may be executed in a shorter time if compared totraditionally managed startup processes. In particularly in largecomplex cloud computing environments with thousands of virtual machines,such a time advantage may prove to be significantly.

In the following further embodiments of the method and the relatedsystem will be described:

According to one preferred embodiment, the method may also comprisesetting an entry of the list with entries of startup processes in a waitstatus if the requirement is not fulfilled. Thus, the process cannot beexecuted as part of the boot sequence if the requirement is notfulfilled. Only those processes may be started as part of the bootsequence which requirements are fulfilled. No attempt is made to start aprocess if the requirement is not fulfilled resulting in unnecessaryerrors messages and/or warnings.

According to an advantageous embodiment, the method may compriseremoving the wait status for the entry if a trigger is received,indicative of a required resource becoming available and satisfying therequirement. Thus, the related process may be started as part of theboot sequence if the requirement is fulfilled. A straight forward bootsequence may be guaranteed without any waste of resource, i.e., to earlyprocess start attempts or a completely blocked boot sequence because notall requirements ought to be fulfilled at one point in time.

According to an optional embodiment of the method, the requirement maybe defined by an explicit configuration setting, e.g., by defining thatone of the requirements may be a minimum of a specific amount of memory,e.g., 1 GB of main memory. Hence, the related process cannot be startedif not 1 GB of contiguous main memory (e.g., in a real or a virtualaddress space) is available.

According to one permissive embodiment of the method, the requirementmay be defined by a measurement or a calculation performed. Thus, as anexample, depending on the related process and/or start parameter valuesfor the process, a minimal input/output throughput rate may be requiredwhich may, as a consequence, require a minimal number of adapters, eachwith a predefined throughput rate.

According to a further advantageous embodiment of the method, therequirement may be a minimal exclusively available resource. This may,e.g., be the case for memory resources which may not be shared amongprocesses.

According to another advantageous embodiment of the method, therequirement may be shared among processes. This may be the case withinput/output adapters which may normally be shared among processes usingthe resource. For input/output adapters, a kind of over-commitment mayalso be allowable.

According to one additionally preferred embodiment of the method, therequirement may be defined by a policy, defining a sequence of dependingprocesses, priorities. Thus, weighing factor values may be defined,organizing a sequence of boot processes if the processes in question maybe started in parallel but requiring the same exclusive resource. Thus,competition between the processes for the same resource may be avoidedwhich may potentially end in a deadlock situation.

According to a further advantageous embodiment of the method, thecomputer system may be a physical computer system or a virtual machine.Hence, there are no limits regarding the type of computer supported bythe concept newly disclosed herein.

According to one useful embodiment of the method, the resource may be ischaracterized or defined by its type and quantity, i.e., an amount ofmemory in GB, a number of input/output adapters or a number of networkconnections. The type and quantity may be defined for a real or avirtual computer system/machine.

In the following, a detailed description of the figures will be given.All instructions in the figures are schematic. Firstly, a block diagramof an embodiment of the inventive computer-implemented method forbooting a computer system is given. Afterwards, further embodiments, aswell as embodiments of the boot module for booting a computer system,will be described.

FIG. 1 shows a block diagram of an embodiment of thecomputer-implemented method 100 for booting a computer system—either areal or a virtual machine. The method comprises providing, 102, a listwith entries of startup processes. This list may be denoted as extendedboot sequence table (BST-E). Each startup process defines aresource—like memory, storage, IOs, CPU(s)—of the computer system. Foreach startup process a requirement—which may be one or morerequirements—is defined.

The method also comprises fetching, 104, one of the entries of the listwith entries of startup processes, determining, 106, whether therequirement is satisfied for the one of the entries of the list withentries of startup processes and fetching, 108, in case the requirementis not fulfilled, a next one of the entries of the list with entries ofstartup processes. Furthermore, the method comprises starting, 110, incase the required resource is fulfilled, the startup process, andrepeating, 112, the fetching a next one of the entries, the determiningand the starting until all startup processes of the list of startupprocesses have been started.

Optionally, more than one resource or startup related requirement may bedefined. Thus, a process may only be started if all conditions arefulfilled.

FIG. 2 shows a block diagram of an embodiment of a known boot process200. A state of the art approach of a boot sequence table comprises astatic list 202 of processes to be started in the listed order. As anexample, the daemon “system” represents the state-of-the-art in Linuxsystems to control the system startup 206 based on so-called services.The boot sequence table may be stored, e.g., on a hard drive 204. Thus,no flexibility exists in traditional startup systems.

The services might depend on another service, having been started oralready in the process of being started (most usual dependency), that aparticular device has become available (e.g., serial console, USBinserted) or that another service has been terminated (e.g., clean-upservice during shutdown).

When such a dependency is matched then ALL dependent services arestarted. It is not possible to define how many services need to becomeavailable, such as “at least 3 USB devices”. It is also not possible todefine “consumption” of a service such as “the service consumes oneserial interface—this serial interface is reserved and not available forother services”. Furthermore, it is not possible to definepriorities—when two or more services to dependencies are met, which oneshould be started first.

Although high availability policies may provide policies to startresources that are based on resource availabilities, resourcedependencies or start orders, they do neither wait for hot clock eventsnor do they consider resource quantities (e.g., specific amount ofavailable memory).

FIG. 3 shows a block diagram 300 of an embodiment of a boot processaccording to the concept disclosed herein and in the context of theknown boot process of FIG. 2. The basic idea of the concept disclosedherein is to extend the boot sequence table with requirements forservices (process), e.g., of the operating system 302. Additionally, anadditional boot sequence daemon 304 (which may also be integrated intothe existing system) may be required which is enabled to handle“Resource Requests” 306 and “Add Resource Events” 308 for executing thecomplete start process 206.

“Add Resource Events” are triggered if a specific resource becomesavailable (available resource 310). They are bound to a resource type sothat only processes depending on this resource type have to beinvestigated by the boot sequence daemon.

As additional input to the start process, the boot sequence table(compare FIG. 2) may be extended to an extended boot sequence table(BST-E) 312. The BST-E is extended by resource requirements for eachprocess that is listed. The requirements may be of different types asshown below.

Instead of the boot sequence table 202 of FIG. 2, the BST-E may now looklike:

TABLE 1 start process a, has requirement x start process b, hasrequirement y start process c, has requirement z

The requirements can either be set explicitly via a configurator or maybe determined by a measurement or calculation.

The requirements can be minimal exclusive—e.g., for an amount ofmemory—or shared—e.g., IO devices—to be able to run. Over-commitmentsmay be allowed for shared devices.

Furthermore, the requirements can be based on a policy, e.g., in theform of a pre-defined sequence (process b depends on process a),priorities or weights. Hence, the one requirement shown in table 1 abovemay be a combination of sub-requirements, each of which may again becross-dependent to other requirements. Thus, a tree of requirements maybe defined.

The above-mentioned boot sequence daemon 304 is running in a loop overthe startup process until all the required start processes that arelisted in the extended boot sequence table 312 are started.

FIG. 4 shows a more comprehensive block diagram 400 of an embodiment ofthe disclosed method 100 which starts at 402. In a first step, it isdetermined whether the BST-E has an incomplete entry, 404. Then, theboot sequence daemon fetches, 408, the next incomplete entry from theBST-E.

If a waiting flag is set for a required resource and if the requiredresources are available (compare 410, 412), the process is started andthe corresponding state entry in the BST-E is set to “complete”, 414.”Then the loop starts from the beginning.

If the required resource is not available, the corresponding state entryfor the process in the BST-E is set to “waiting”. If the resource is notavailable, the boot sequence daemon fetches, 416, a next incompleteentry from the BST-E. If there are more entries in the BST-E, 418, thewait sub-process 420 is started.

If the BST-E has no additional incomplete entries—case no ofdetermination 404—this process ends, 406.

FIG. 5 shows an embodiment of the wait sub-process 420 of FIG. 4. Thewait sub-process 420 starts at 502. Firstly, it is determined, 504,whether an add resource request (ARE) has been received. In case of yes,the boot sequence daemon sets, 508, all entries of the BST-E that arerelated to this type of resource and that are in state “waiting” tostate “incomplete”.

Otherwise, the wait cycle 506 is started and the next loop cyclecontinues after the wait cycle is complete.

It may be noted that a comment box 510 is pointing to the determination504. This may be an indication for the fact that the Add Resource Events(ARE) are queued in the Add Resource Event queue until they areprocessed.—The wait sub-process 420 ends at 502.

FIG. 6 shows a simplified state transition diagram 600 for a stateengine corresponding to the disclosed method 100. Each entry starts andstays “incomplete” 602. In the beginning and on each Add Resource Event,the entries with state “incomplete” are checked. If the requiredresources to start the process of this entry are not sufficient, it isset to “waiting”, 604. If the resources are sufficient, the entry is setto “complete”, 606.

On an Add Resource Event (ARE) all entries that have matching resourcerequirements are set to state “incomplete”, 602.

FIG. 7 shows an embodiment of a boot module 700 for booting a computersystem. The boot module 700 comprises an extended boot sequence tableproviding unit 702 configured to provide a list with entries of startupprocesses. The startup process defines a resource of the computersystem. For each startup process a requirement is defined, as explainedin the context of FIG. 3.

The boot module 700 comprises also a fetching unit 704 configured tofetch one of the entries of the list with entries of startup processesand a determining unit 706 configured to determine whether therequirement is satisfied for the one of the entries of the list withentries of startup processes.

The fetching unit 704 is also configured to fetch, in case therequirement is not fulfilled, a next one of the entries of the list withentries of startup processes and a start module 706 is configured tostart the startup process, in case the required resource is fulfilled.

In the boot module 700 the fetching unit 704, the determining unit 706and the start unit 708 are in combination configured to repeat thefetching a next one of the entries, the determining and the startinguntil all startup processes of the list of startup processes have beenstarted.

FIG. 8 shows a cloud computing environment 800 in which at least partsof the inventive concept may be deployed. A set of functionalabstraction layers provided by a cloud computing environment is shown.It should be understood in advance that the components, layers, andfunctions shown in FIG. 8 are intended to be only illustrative andembodiments of the invention are not limited thereto. As depicted, thefollowing layers and corresponding functions are provided: hardware andsoftware layers 802 include hardware and software components. Examplesof hardware components include: mainframes 804; servers 806; RISC(Reduced Instruction Set Computer) architecture-based servers 808; bladeservers 810; storage devices 812; networks 814 and networking components814. In some embodiments, software components include networkapplication server software 816 and/or database software 818.

A virtualization layer 820 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers822; virtual storage 824; virtual networks 826, including virtualprivate networks; virtual applications and operating systems 828; andvirtual clients 830. In one example, management layer 832 may providethe functions described below. Resource provisioning 834 providesdynamic procurement of computing resources and other resources that areutilized to perform tasks within the cloud computing environment.Metering and pricing 836 provide cost tracking as resources are utilizedwithin the cloud computing environment, and billing or invoicing forconsumption of these resources. In one example, these resources maycomprise application software licenses. Security provides identityverification for cloud consumers and tasks as well as protection fordata and other resources. User portal 838 provides access to the cloudcomputing environment for consumers and system administrators. Servicelevel management 840 provides cloud computing resource allocation andmanagement such that required service levels are met. Service LevelAgreement (SLA) planning and fulfillment 842 provides pre-arrangementfor, and procurement of, cloud computing resources for which a futurerequirement is anticipated in accordance with an SLA.

Workload layer 844 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 846; software development and lifecycle management 848;virtual classroom education delivery 850; data analytics processing 852;transaction processing 854; and boot module 700 for booting a computersystem.

Embodiments of the invention may be implemented together with virtuallyany type of computer, regardless of the platform being suitable forstoring and/or executing program code (real or virtual). FIG. 9 shows,as an example, a computing system 900 suitable for executing programcode related to the disclosed method.

The computing system 900 is only one example of a suitable computersystem and is not intended to suggest any limitation as to the scope ofuse or functionality of embodiments of the invention described herein.Regardless, computer system 900 is capable of being implemented and/orperforming any of the functionality set forth hereinabove. In thecomputer system 900, there are components, which are operational withnumerous other general purpose or special purpose computing systemenvironments or configurations. Examples of well-known computingsystems, environments, and/or configurations that may be suitable foruse with computer system/server 900 include, but are not limited to,personal computer systems, server computer systems, thin clients, thickclients, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputer systems, mainframe computersystems, and distributed cloud computing environments that include anyof the above systems or devices, and the like. Computer system/server900 may be described in the general context of computersystem-executable instructions, such as program modules, being executedby a computer system 900. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 900 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in the figure, computer system/server 900 is shown in the formof a general-purpose computing device. The components of computersystem/server 900 may include, but are not limited to, one or moreprocessors or processing units 902, a system memory 904, and a bus 906that couples various system components including system memory 904 tothe processor 902. Bus 906 represents one or more of any of severaltypes of bus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus. Computersystem/server 900 typically includes a variety of computer systemreadable media. Such media may be any available media that is accessibleby computer system/server 900, and it includes both, volatile andnon-volatile media, removable and non-removable media.

The system memory 904 may include computer system readable media in theform of volatile memory, such as random access memory (RAM) 908 and/orcache memory 910.

Computer system/server 900 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 912 may be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a ‘hard drive’). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a ‘floppy disk’), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media may be provided.In such instances, each can be connected to bus 906 by one or more datamedia interfaces. As will be further depicted and described below,memory 904 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

The program/utility, having a set (at least one) of program modules 916,may be stored in memory 904 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 916 generally carry out the functionsand/or methodologies of embodiments of the invention as describedherein.

The computer system/server 900 may also communicate with one or moreexternal devices 918 such as a keyboard, a pointing device, a display920, etc.; one or more devices that enable a user to interact withcomputer system/server 900; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 900 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 914. Still yet, computer system/server 900may communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 922. As depicted, network adapter 922may communicate with the other components of computer system/server 900via bus 906. It should be understood that although not shown, otherhardware and/or software components could be used in conjunction withcomputer system/server 900. Examples, include, but are not limited to:microcode, device drivers, redundant processing units, external diskdrive arrays, RAID systems, tape drives, and data archival storagesystems, etc.

Additionally, a boot module 700 for booting a computer system may beattached to the bus system 906.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinaryskills in the art without departing from the scope and spirit of thedescribed embodiments. The terminology used herein was chosen to bestexplain the principles of the embodiments, the practical application ortechnical improvement over technologies found in the marketplace, or toenable others of ordinary skills in the art to understand theembodiments disclosed herein.

The present invention may be embodied as a system, a method, and/or acomputer program product. The computer program product may include acomputer readable storage medium (or media) having computer readableprogram instructions thereon for causing a processor to carry outaspects of the present invention.

The medium may be an electronic, magnetic, optical, electromagnetic,infrared or a semi-conductor system for a propagation medium. Examplesof a computer-readable medium may include a semi-conductor or solidstate memory, magnetic tape, a removable computer diskette, a randomaccess memory (RAM), a read-only memory (ROM), a rigid magnetic disk andan optical disk. Current examples of optical disks include compactdisk-read only memory (CD-ROM), compact disk-read/write (CD-R/W), DVDand Blu-Ray-Disk.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including anobject-oriented programming language such as Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus', and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus', or anotherdevice to cause a series of operational steps to be performed on thecomputer, other programmable apparatus or other device to produce acomputer implemented process, such that the instructions which executeon the computer, other programmable apparatus', or another deviceimplement the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowcharts and/or block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or act or carry out combinations of special purpose hardwareand computer instructions.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to limit the invention. As usedherein, the singular forms “a”, “an” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will further be understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or steps plus function elements in the claims below are intendedto include any structure, material, or act for performing the functionin combination with other claimed elements, as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skills in the artwithout departing from the scope and spirit of the invention. Theembodiments are chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skills in the art to understand the invention forvarious embodiments with various modifications, as are suited to theparticular use contemplated.

What is claimed is:
 1. A computer-implemented method for booting acomputer system, comprising: producing an extended boot sequence table(BST-E) with respect to a plurality of startup processes, where for eachstartup process, the BST-E includes a computer system resourcerequirement; determining, with respect to each startup process, whethera corresponding computer system resource requirement is satisfied; foreach startup process, on condition the corresponding system resourcerequirement is not satisfied, placing the startup process in a waitstatus; receiving a trigger indicative of a resource becoming available,the resource satisfying a computer system resource requirement for acorresponding startup process that is in the wait status; and startingthe corresponding startup process having the wait status.
 2. The methodaccording to claim 1, wherein starting the corresponding startup processhaving the wait states includes: removing the wait status from thecorresponding startup process.
 3. The method according to claim 1,wherein the computer system resource requirement is defined by anexplicit configuration setting.
 4. The method according to claim 1,wherein the computer system resource requirement is defined by ameasurement or calculation.
 5. The method according to claim 1, whereinthe computer system resource requirement is a minimal exclusivelyavailable resource.
 6. The method according to claim 1, wherein thecomputer system resource requirement is shared among processes.
 7. Themethod according to claim 1, wherein the computer system resourcerequirement is defined by a policy defining a sequence of dependingprocesses, priorities, or weights.
 8. The method according to claim 1,wherein the computer system is a physical computer system or a virtualmachine.
 9. The method according to claim 1, wherein the computer systemresource requirement is characterized by a type and a quantity.
 10. Acomputer system for booting a computer system, comprising: one or morecomputer processors; one or more computer readable storage media;computer program instructions; the computer program instructions beingstored on the one or more computer readable storage media for executionby the one or more computer processors; and the computer programinstructions comprising instructions to: produce an extended bootsequence table (BST-E) with respect to a plurality of startup processes,where for each startup process, the BST-E includes a computer systemresource requirement; determine, with respect to each startup process,whether a corresponding computer system resource requirement issatisfied; for each startup process, on condition the correspondingsystem resource requirement is not satisfied, place the startup processin a wait status; receive a trigger indicative of a resource becomingavailable, the resource satisfying a computer system resourcerequirement for a corresponding startup process that is in the waitstatus; and start the corresponding startup process having the waitstatus.
 11. The computer system according to claim 10, wherein theinstructions to start the corresponding startup process having the waitstates include instructions to: remove the wait status from thecorresponding startup process.
 12. The computer system according toclaim 10, wherein the computer system resource requirement is defined byan explicit configuration setting.
 13. The computer system according toclaim 10, wherein the computer system resource requirement is defined bya measurement or calculation.
 14. The computer system according to claim10, wherein the computer system resource requirement is a minimalexclusively available resource.
 15. The computer system according toclaim 10, wherein the computer system resource requirement is sharedamong processes.
 16. The computer system according to claim 10, whereinthe computer system resource requirement is defined by a policy defininga sequence of depending processes, priorities, or weights.
 17. Thecomputer system according to claim 10, wherein the computer system is aphysical computer system or a virtual machine.
 18. The computer systemaccording to claim 10, wherein the computer system resource requirementis characterized by a type and a quantity.
 19. A computer programproduct for booting a computer system, the computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions beingexecutable by a computing system to cause the computing system to:produce an extended boot sequence table (BST-E) with respect to aplurality of startup processes, where for each startup process, theBST-E includes a computer system resource requirement; determine, withrespect to each startup process, whether a corresponding computer systemresource requirement is satisfied; for each startup process, oncondition the corresponding system resource requirement is notsatisfied, place the startup process in a wait status; receive a triggerindicative of a resource becoming available, the resource satisfying acomputer system resource requirement for a corresponding startup processthat is in the wait status; and start the corresponding startup processhaving the wait status.
 20. The computer program product according toclaim 19, wherein the instructions to start the corresponding startupprocess having the wait states include instructions to: remove the waitstatus from the corresponding startup process.